|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2047 (1996)
|
|
Title:
|
MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
|
|
|
2.
|
Status of approval:
|
|
|
Draft Standard. Updated by RFC 2184, RFC 2231
|
|
3.
|
Justification for the specific reference:
|
|
|
This recommendation uses encoded headers from section 2 of the reference.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/draft=&rfc=2047&doctitle=&group=&holder=&iprtitle=&patent=&submit=rfc
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 2047 was published in November 1996 and is a standards track RFC. Current status: Draft Standard.
A Draft Standard is normally considered to be a final specification, and changes are likely to be made only to solve specific problems encountered. In most circumstances, it is reasonable for vendors to deploy implementations of Draft Standards into a disruption sensitive environment.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 2047 was published in November 1996 and is a standards track RFC.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Obsoletes: RFCs 1521, 1522, 1590. Updated by: RFC 2184, RFC 2231
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
None.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
